forked from buildroot/buildroot
-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] master from buildroot:master #335
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Scott Fan <fancp2007@gmail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Signed-off-by: Scott Fan <fancp2007@gmail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Fixes the following security issue: CVE-2024-48423: An issue in assimp v.5.4.3 allows a local attacker to execute arbitrary code via the CallbackToLogRedirector function within the Assimp library assimp/assimp#5788 https://www.cve.org/CVERecord?id=CVE-2024-48423 Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
For release note, see: https://github.com/yhirose/cpp-httplib/releases/tag/v0.19.0 Signed-off-by: Aleksandr Makarov <aleksandr.o.makarov@gmail.com> [Julien: add link to release note] Signed-off-by: Julien Olivain <ju.o@free.fr>
Release notes: https://github.com/timescale/timescaledb/blob/2.18.1/CHANGELOG.md Signed-off-by: Scott Fan <fancp2007@gmail.com> Reviewed-by: Maxim Kochetkov <fido_max@inbox.ru> Signed-off-by: Julien Olivain <ju.o@free.fr>
Release-notes: https://github.com/osmcode/libosmium/releases/tag/v2.21.0 Bump minimal GCC version to 5. (Switched to C++14 as minimum requirement) osmcode/libosmium@a83fbf8 Remove support for projection using the Proj library osmcode/libosmium@711721c Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru> Signed-off-by: Julien Olivain <ju.o@free.fr>
The autosetup script will skip checking for readline.h when cross-compiling, which will cause line-editing support for the sqlite3 shell to always be "none". In this case, if the --editline option is provided, an error will be reported: ERROR: Explicit --editline failed to find a matching library. However, we can enable readline or editline support by specifying the CFLAGS and LDFLAGS values instead of having it handled automatically by the autosetup configure script. In addition, the libedit package actually depends on the ncurses package, just like the readline package. So when using the libedit package, also add the ncurses dependency. Tested-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Scott Fan <fancp2007@gmail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
….49.0 Buildroot commit [1] bumped sqlite to 3.49.0, and commit [2] fixed the package infra. But if the toolchain does not have C++ support enabled, the following error will occur. Error: failed to find: no The reason was CXX has been set to 'no' in the package/Makefile.in file. ifneq ($(BR2_INSTALL_LIBSTDCPP),y) TARGET_CONFIGURE_OPTS += CXX=no endif Then the autosetup script will look for a required path ('no' above), and will exit with an error if not found. To solve it, we can set CXX to 'false' instead of 'no', so that the autosetup script will skip checking for a C++ compiler. Fixes: https://autobuild.buildroot.org/?reason=sqlite-3.49.0 https://autobuild.buildroot.org/results/569a3750681cc10688ac663450dc2773a317bb07/ [1] https://gitlab.com/buildroot.org/buildroot/-/commit/db85638cea3414ca0293cbbb2352e5b0b63a2579 [2] https://gitlab.com/buildroot.org/buildroot/-/commit/a93680be30bc35f7d2465ef576035fb937ea1d64 Signed-off-by: Scott Fan <fancp2007@gmail.com> [Julien: add a link to an actual build failure] Signed-off-by: Julien Olivain <ju.o@free.fr>
Add support to binutils-bare-metal to support multiple architecture tuples with the BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH string. To do this, custom configure, build and install commands are needed, so that each step goes through a loop of the architecture tuples in the list. To keep consistency with autotools, all the relevant host configurations have been copied into the HOST_BINUTILS_BARE_METAL_CONF_OPTS while removing any configurations that do not apply to binutils and removing redundant configs. autotools redundant configs covered by $(HOST_CONFIGURE_OPTS): CFLAGS="$$(HOST_CFLAGS)" LDFLAGS="$$(HOST_LDFLAGS)" autotools configs not applicable to binutils: --disable-gtk-doc --disable-gtk-doc-html --disable-doc --disable-docs --disable-documentation --disable-debug --with-xmlto=no --with-fop=no --disable-nls One of the configurations already in the binutils-bare-metal package was not needed. --enable-static -> handled by --disable-shared Signed-off-by: Neal Frager <neal.frager@amd.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Add support to gcc-bare-metal to support multiple architecture tuples with the BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH string. To do this, custom configure, build and install commands are needed, so that each step goes through a loop of the architecture tuples in the list. To keep consistency with autotools, all the relevant host configurations have been copied into the HOST_GCC_BARE_METAL_CONF_OPTS while removing any configurations that do not apply to gcc and removing redundant configs. autotools redundant configs covered by $(HOST_CONFIGURE_OPTS): CFLAGS="$$(HOST_CFLAGS)" LDFLAGS="$$(HOST_LDFLAGS)" autotools configs not applicable to gcc: --disable-gtk-doc --disable-gtk-doc-html --disable-doc --disable-docs --disable-documentation --disable-debug --with-xmlto=no --with-fop=no --disable-nls While we're at it: the following configuration option was incorrect: --disable-initfini_array -> --disable-initfini-array configure converts - to _ anyway so it makes no difference, but it's better to be consistent. Signed-off-by: Neal Frager <neal.frager@amd.com> [Arnout: keep --disable-libstdcxx-pch and better explanation for --disable-initfini-array] Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Add support to gcc-bare-metal to support multiple architecture tuples with the BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH string. To do this, custom configure, build and install commands are needed, so that each step goes through a loop of the architecture tuples in the list. To keep consistency with autotools, all the relevant target configurations have been copied into the NEWLIB_BARE_METAL_CONF_OPTS while removing any configurations that do not apply to newlib. Also, the following configs were not taken because newlib is being built for each of the bare-metal targets and not the main target of Buildroot. $$(TARGET_CONFIGURE_OPTS) $$(TARGET_CONFIGURE_ARGS) --target=$$(GNU_TARGET_NAME) --host=$$(GNU_TARGET_NAME) Signed-off-by: Neal Frager <neal.frager@amd.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
…le tuple support Now that binutils-bare-metal, gcc-bare-metal and newlib-bare-metal packages have been upgraded to support a list of architecture tuples, this patch updates the toolchain-bare-metal-buildroot help text to describe the new capability. BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH is still backwards compatible with its prior definition as defining a single tuple with this new definition works exactly the same as before. Signed-off-by: Neal Frager <neal.frager@amd.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Now that BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH can contain multiple tuples, BR2_TARGET_XILINX_EMBEDDEDSW can no longer be dependent on: depends on BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH = "microblazeel-xilinx-elf" A valid definition could have "microblazeel-xilinx-elf" as just one of many tuples in the list. For this reason, this patch changes the dependency to: depends on BR2_TOOLCHAIN_BARE_METAL_BUILDROOT One side effect of this is that the user comment will be displayed now when using multiple tuples, even if one of them is the required tuple. Signed-off-by: Neal Frager <neal.frager@amd.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )